System and method for using a computer as a bridge for data synchronization between a cellular device and a computer network

ABSTRACT

A method for data bridging and synchronization between a mobile device and a computer network, using a computer connected to the mobile device over a short range communication channel.

This Application claims priority from U.S. Provisional Application No.61/136,583, filed on Sep. 17, 2008 which is hereby incorporated byreference in its entirety as if fully set forth herein.

FIELD OF THE INVENTION

The present invention is of a system and method for synchronizationbetween a cellular device and a computer network, using a computer as abridge.

BACKGROUND OF THE INVENTION

Digitally enabled telephones and other connected devices, includingcellular telephones, are all able to be connected to a data network.Unlike simple analog telephones, this ability to communicate with aserver increases the variety and type of services which may be offeredthrough such telephones.

Short range wireless communication protocols, such as Bluetooth andinfrared (IR) are now available in most of the cellular phones andenable wireless communication, short range communication between amobile devices such as cellular telephone and a computer (PC) forvarious purposes such as, for example transferring files and the like.

The computer, with which the cellular telephone is communicating, isusually connected to the internet through a wired or a wirelesscommunication, providing for long range communication. New cellulartechnologies such as the third generation cellular technology enableusers to upload or download data from a cellular device to a serverconnected to the internet via cellular network. Such uploading anddownloading can be used, for example for synchronizing data residing inthe mobile device such as cellular telephone, for example calendarinformation with an external server connected to the internet network.Such data transfer may be utilized for many purposes for example foruploading pictures to internet applications such as Flickr, Picasa,Facebook (social networks) or the like.

However the use of cellular internet technology for data transmissionposses a problem in that it is expensive, not reliable and may cause aheavy traffic on the cellular network itself. In addition suchtechnologies have bandwidth limitation which makes the downloading andespecially uploading inconvenient.

Unfortunately, there is no such solution which facilitates the potentialin connecting a cellular device to the internet via a computer. Suchconnection can allow users to easily transfer data between theircellular device and the internet “cloud”, without worrying about thecost of using the cellular network. Such connection can also improve thebandwidth and in particular when uploading data. Such connection canalso enable user to transmit or receive data even when there is notconnected to the cellular network or when the feature for connecting tothe internet via cellular network is not available.

SUMMARY OF THE INVENTION

There is thus an unmet need for, and it would be highly useful to have areliable and inexpensive method and system for transferring data betweena mobile device such as a cellular telephone, and a server connected tothe internet or other computer network. There is also an unmet need thatprovides users with higher bandwidth for downloading and, in particular,for uploading data. It is known in the art that upload links forcellular telephones have much lower bandwidth than download links.

There is also an unmet need, and it would be highly useful to enablemobile device users that are not connected to a cellular data network(temporarily or permanently), to be connected to internet or othercomputer network servers for transferring and receiving data.

The present invention overcomes the deficiencies of the background artby providing system and method for data synchronization between a mobiledevice, for example a cellular telephone, or mobile telephone, and acomputer network through a computer, bridging between the cellulardevice and the Internet.

Before turning to a description of the present invention, a list ofabbreviations is provided:

Abbreviations CDMA, Code Division Multiple Access ESN, Electronic SerialNumber HTTP, HyperText Transfer Protocol HTTPS, HTTP Secure IMEI,International Mobile Equipment Identity MMS, Multimedia MessagingService MSISDN, Mobile Subscriber ISDN Number PC, Personal Computer SIM,Subscriber Identity Module SIP, Session Initiation Protocol SMS, ShortMessage Service SyncML, Synchronization Markup Language UI, UserInterface

Within the context of this application the term agent refers to softwareand/or firmware application for facilitating and/or controlling datacommunication for example synchronization between a device and a server.Data communication may optionally be provided with wirelesscommunication, cellular, WiFi, BlueTooth, IR, wired, or the like. Anagent is described in US Patent publication US 2009/0177800 which isincorporated herein by reference as if fully set forth.

Within the context of this application the terms “data push” or “push”refers to data that is being transferred between a sender and receiverwhere the data transfer process is controlled by the sender.

Within the context of this application the term “data pull” or “pull”refers to data that is being transferred between a sender and receiverwhere the data transfer process is controlled by the receiver.

Within the context of this application the term mobile device may betinterchangeably used with the term cellular device to refer to anymobile device that may be linked to a cellular network, for example acellular telephone, PDA, Portable Media Player (PMP), netbook, laptopcomputer or the like mobile device.

Within the context of this application the term server refers to anycontent provider server, for example a third generation mobile telephoneservice provider. According to an optional embodiment, the presentinvention is simple to install, configure and use, and enables todownload and upload data to a server connected to a computer networksuch as the internet, for purposes such as backup information residingin the cellular device, or for transferring data to/from internetapplications. Such applications can be, for example Google (contacts andcalendar) YouTube (video uploading and sharing), Facebook (socialnetworks) and the like. Such data can be, for example, pictures and thelike. The present invention enables access to server located on thecomputer network regardless of its location. The present inventionrelates to any type of computer network but is described herein withregard to the Internet for the purpose of description only and withoutany intention of being limiting in any way.

According to one embodiment of the present invention, the data istransferred from the cellular device to the computer via wireless orwired short range connections, also known as Personal Area Network(PAN). Such wireless connections can be, for example Bluetooth,Infrared, UWB, Z-Wave, ZigBee and the like. Wired connection can be, forexample USB cable, FireWire and the like. The protocol for transferringthe data can optionally be a proprietary protocol or OBEX (Objectexchange). OBEX (abbreviation of OBject EXchange, also termed IrOBEX) isa communications protocol that facilitates the exchange of binaryobjects between devices. It is maintained by the Infrared DataAssociation but has also been adopted by the Bluetooth Special InterestGroup and the Data Synchronization protocol (SyncML) of the Open MobileAlliance (OMA). The proprietary protocol, according to the invention,includes a flexible and fault-tolerant mechanism of splitting largeamount of data (textual or binary) into multiple chunks, thus dealingwith memory and networking constraints of each device.

The data from the computer to the server is transferred via protocolssuch as HTTP and the like. The application resides on the computeroptionally and preferably is able to bridge (i.e. translate) betweenprotocols and transfer the data from the cellular device to the serverand vice versa.

According to other embodiment of the present invention, the datatransferred from the cellular device to the computer can be eitherpushed or pull. If pull, then the cellular device might not have anagent, since the built-in Bluetooth capabilities of the phone can beused. If pushed, then the agent in the cellular device periodically, orupon request, transfers the data to from the cellular device to thecomputer. Pulling the data by the computer can optionally enable theaccessing to specific data such as message inbox or file system (e.g.,Bluetooth FTP profile), which may not reachable by the agent which isinstalled on the cellular device.

According to another embodiment of the present innovation, the servercan communicate with one or more computers for transmitting/receivingdata from cellular devices. The cellular device can optionally andadditionally communicate directly with the server (in the case that thecellular device is not connected to a computer).

According to another embodiment of the present innovation, the servercan store data received from cellular device, for back-up purposes, forexample. Such data can be, for example personal address book, calendarand the like.

According to another embodiment of the present innovation, the servercan communicate with other (third party) servers connected to theinternet for transferring data received from the cellular devices. Suchservers can be, for example, media sharing and social networkingservices, such as for YouTube or Facebook.

According to another embodiment of the present invention, the user candefine the connection type to the Computer (Bluetooth, infrared and thelike). The user can optionally define whether the data will be pushed tothe computer or pulled (in the latter case an agent is not required tobe installed in the cellular device). The user can also schedule thetime for pushing or pulling the data or, additionally or alternativelydownload or upload the data on demand. The user can also optionallydefine the type of data that should automatically be transferred and thedestinations.

The cellular device, according to this invention, can be any device withan access to a cellular network. Such device can be for example a, acellular telephone, a PDA and the like. The cellular device isoptionally and preferably capable of one or more of voice and/or videocommunication, messaging (more preferably one or more of SMS, MMS orEMS) or the like; for example the communication device is optionally acellular telephone, or PDA. The cellular telephone preferably is able tocommunicate with a computer through a wire or wireless short rangecommunication channel; such wireless communication can use, for example,Bluetooth, infrared, USB cable and the like. The cellular devicepreferably contains some kind of local storage, including but notlimited to a flash memory, memory card, SIM card or a hard disk.Optionally and preferably the device is capable of voice and/or videocommunication.

The cellular telephone may also optionally be characterized as a limitedresource device. Hereinafter, the term “limited-resource device” refersto a computational device in which computational resources such asmemory, storage space, network bandwidth and/or data processingcapabilities are limited, particularly in comparison to desktopcomputers such as PCs (personal computers), for example.

By “computer” it meant any computer which has short range communicationcapabilities, such as Bluetooth and/or infrared access and also has anaccess to the internet or other computer network.

Unless otherwise defined, all technical and scientific terms used hereinhave the same meaning as commonly understood by one of ordinary skill inthe art to which this invention belongs. The materials, methods, andexamples provided herein are illustrative only and not intended to belimiting.

Implementation of the method and system of the present inventioninvolves performing or completing certain selected tasks or stepsmanually, automatically, or a combination thereof. Moreover, accordingto actual instrumentation and equipment of preferred embodiments of themethod and system of the present invention, several selected steps couldbe implemented by hardware or by software on any operating system of anyfirmware or a combination thereof. For example, as hardware, selectedsteps of the invention could be implemented as a chip or a circuit. Assoftware, selected steps of the invention could be implemented as aplurality of software instructions being executed by a computer usingany suitable operating system. In any case, selected steps of the methodand system of the invention could be described as being performed by adata processor, such as a computing platform for executing a pluralityof instructions.

A cellular device as term herein may be any device that can transferdata through the cellular network or through a wired connection, as wellas through a short range wireless connection such as Bluetooth orinfrared, or through a direct wired connection to a local device orcomputer.

Although the present invention is described with regard to a “device” ona “wireless network”, featuring a “server” and preferably for cellularcommunication, it should be noted that optionally any device featuring adata processor and/or the ability to execute one or more instructionswith the ability to support at least voice communication may bedescribed as a telephone, including but not limited to any type oftelephone enabled computer, a cellular telephone, an IP telephone(software (virtual) device or real (hardware) device), a smart phone, aPDA (personal digital assistant), or a pager. Any two or more of suchdevices in communication with each other, and/or any computer incommunication with a telephone may optionally comprise a “wirelessnetwork”, which may (for example) optionally be a computer networkand/or a cellular network.

A “server” as termed herein may optionally comprise any computer that isconnected to an IP network. It should be noted that optionally anydevice featuring a data processor and/or the ability to execute one ormore instructions may be described as a computer, including but notlimited to a PC (personal computer), a server, a minicomputer. Any twoor more of such devices in communication with each other, and/or anycomputer in communication with any other computer may optionallycomprise a “computer network”.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention is herein described, by way of example only, withreference to the accompanying drawings. With specific reference now tothe drawings in detail, it is stressed that the particulars shown are byway of example and for purposes of illustrative discussion of thepreferred embodiments of the present invention only, and are presentedin order to provide what is believed to be the most useful and readilyunderstood description of the principles and conceptual aspects of theinvention. In this regard, no attempt is made to show structural detailsof the invention in more detail than is necessary for a fundamentalunderstanding of the invention, the description taken with the drawingsmaking apparent to those skilled in the art how the several forms of theinvention may be embodied in practice.

In the drawings:

FIG. 1A is a schematic block diagram of an exemplary system according tothe present invention comprising an agent installed in the cellulardevice; and

FIG. 1B is a schematic block diagram of an exemplary system according tothe present invention without an agent on the cellular device; and

FIG. 2 is a schematic block diagram for transferring data from thecellular device to a content provider server via the computer.

FIG. 3 A is a schematic diagram describing the push scenario in onlinemode.

FIG. 3 B is a schematic diagram describing the push scenario in offlinemode.

FIG. 4 A is a schematic diagram describing the pull scenario in onlinemode.

FIG. 4 B is a schematic diagram describing the pull scenario in offlinemode.

FIG. 5 is a schematic diagram describing the connections in the system.

FIG. 6 is a detailed description of the proxy authentication process.

FIG. 7 is a detailed description of the PC to server authentication.

FIG. 8 is a detailed description of the double authentication.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

The present invention is of a system and method for data bridging andsynchronization between a mobile device and a computer network. Forexample and without wishing to be limited or to imply a closed list, fora cellular telephone or other device that communicates through acellular network, the many advantages include but are not limited tolower cost, and increased bandwidth and reliability. For devices thatuse WiFi or WiMax, or other similar wireless but non-cellularcommunication protocols, the many advantages include but are not limitedto availability since the network coverage is limited, and also to atleast some extent increased bandwidth and reliability. For other typesof wireless communication protocols, the many advantages may include butare not limited to any of the above, as well as any other advantagesthat accrue from use of bridging as described herein.

COMMON TERMS

-   Mobile device 102-   Server 104-   Agent 108-   Mobile device memory 112-   Server memory 114-   Computer 115

Referring now to the drawings, FIGS. 1A-B show schematic block diagramsof an optional systems 100 (FIG. 1A) and 101 (FIG. 1B), according to afirst, second and third embodiments of the present invention providingfor data bridging and synchronization between a network server 104 and amobile device 102 optionally and preferably by computer 115.

Most preferably data bridging and synchronization in systems 100 and 101according to optional embodiments of the present invention is providedby an agent 108 optionally provided as a thin client or the like as isknow in the art.

Agent 108 may be activated to facilitate communication between mobiledevice 102 and server 104 through a bridge most preferably provided bycomputer 115 by at least one or more modes of activation for exampleincluding but not limited to remote activation, automatic activation,manual activation, taken alone or in any combination thereof. Optionallytwo or more activation modes may be utilized essentially simultaneouslyto activate agent 108.

Optionally remote activation of agent 108 is optionally initiated by atleast one or more of server 104, mobile device 102 or computer 115 thatis not physically associated with agent 108. For example, as depicted inFIG. 1A agent 108 is associated with mobile device 102 wherein remoteactivated may optionally be provided by at least one of or both server104 and/or computer 115. Most preferably, remote activation may beprovided by server 104. For example, server 104 may optionally initiatesuch agent 108 activation through a Communication Initiation Request(CIR) or through like protocols. For example a CIR is sent by server 104to activate agent 108.

Optionally automatic activation of agent 108 may be initiated by atriggered event and/or occurrence taking place in at least one or moreof mobile device 102, server 104 or computer 115. Optionally a triggeredevent may for example include but is not limited to a time dependentevent, time lapse, scheduled event, missed event, milestone crossing,hardware event, hardware coupling, software event, software coupling,wireless device coupling, system event, processor reboot, useriteration, sending and/or receiving a trigger, SMS, automatic voiceactivation, geographical displacement, roaming event, association withan auxiliary device, association with a device, a sensed event or thelike triggering event taken alone or in any combination thereof.

Optionally manual activation may be initiated by at least one or moreuser, optionally by interacting with hardware and/or software associatedwith at least one of mobile device 102, server 104 and/or computer 115that is associated with agent 108. Most preferably manual initiation istriggered by a user interacting with mobile device 102 comprising agent108. For example, a user may manually activate agent 108 through anavailable menu option associated with device 102.

Optionally and preferably following activation agent 108 functions tofacilitate data bridging and synchronization between at least two datastores associated with at least two devices for example including butnot limited to mobile devices 102, server 104 and/or computer 115. Mostpreferably data is bridged between mobile device 102 and server throughcomputer 115. Agent 108 may optionally provide data synchronization fora plurality of data types common to at least two devices for exampleincluding but not limited to mobile device 102, computer 115 and server104. Synchronized data may for example include but is not limited tocontact information, address book data, calendar events (including butnot limited to meetings, anniversaries, birthdays, holidays,appointments, reminders, etc.), tasks (i.e. “to do”), messages, SMS,media files, image data, audio data, video data or the like, documentsand/or other files.

Most preferably a communication bridge is established between server 104and device 102 via a communication bridge comprising at least onecommunication channel and more preferably at least two communicationchannels. A first communication channel 117 is preferably establishedbetween mobile device 102 and computer 115. Optionally firstcommunication channel 117 is most preferably provided in the form of alocal peer-to-peer connection providing for local and/or short rangecommunication between device 102 and computer 115, for example includingbut not limited to short range communication technology, short rangecommunication protocols such as wired, Bluetooth, IR, optical, acousticor the like short range communication technology and/or protocols as isknown in the art.

Preferably and optionally, a second communication channel 118 ispreferably provided to establish communication between computer 115 andserver 104 for example including wired, wireless, telephone network,internet or the like communication protocols as is known in the arttaken alone or in any combination thereof. Optionally and preferablycommunication channel 118 provides for long range communication betweencomputer 115 and server 104.

Optionally and preferably once at least one and more preferably twocommunication channels are established data synchronization may beinitiated.

Optionally and preferably data synchronization may be performed betweenat least two data stores associated with at least two of mobile device102, server 104 or computer 115. Most preferably data may be sharedbetween the different devices and stored in different formats specificto each of the devices and applications where synchronization isperformed. For example, mobile device 102 and server 104 save contactdetails using file format A while computer 115 stores contact detailsusing file format B most preferably synchronization process provides forconverting in between the various formats, for example A to B to A orthe like, as is necessary to ensure complete data synchronization anddata integrity.

Optionally data synchronization may be performed in at least one or moremethods for example online (synchronous) or offline (asynchronous)configurations. Most preferably, the method utilized for synchronizationis determined communication channels established; optionally onlinesynchronization is performed when at least two communication channels117 and 118 are established; optionally offline synchronization isperformed where at least one of communication channels 117 or 118 isestablished.

Most preferably online synchronization is performed when bothcommunication channels 117 and 118 are established and functioning.Optionally and preferably online synchronization is facilitated by async application associated with computer 115. Optionally and preferablysync application (not shown here see FIGS. 3-4) enables computer 115 toact as a proxy between mobile device 102 and server 104, in bothdirections. Optionally computer sync application enables computer 115 tostore a copy of the synchronized and/or transferred data.

Online synchronization may optionally be initiated by agent 108 wheredata stored on mobile device 102 is read to identify data changes forexample, data modified, added and/or deleted in mobile device 102 sincethe last synchronization was performed. Optionally, any changes to thedata may be performed by at least one or more methods for datacomparison as is known in the art for example including but not limitedto checksum and/or timestamp comparison or the like as is known in theart. Next, once changes are identified they are communicated to computer115 through communication channel 117. Optionally, a sync application oncomputer 115 may store the transmitted data from mobile device 102.Next, computer 115 transmits the mobile device changed data to server104 through communication channel 118. Next, server 104 identifies datachanges for example, modified, added and/or deleted data associated withserver 104 since the last synchronization was performed, andcommunicates data changes to computer 115 through communication channels118. Next, computer 115 communicates the server 104 changed data tomobile device 102 for writing. Optionally computer 115 may store thecommunicated data received from server 104. Finally, computer 115provides server 104 with mapping data from mobile device 102, forexample one or more local identifiers associated with mobile device 102are associated with global identifiers associated with server 104.Various synchronization procedures feature such a mapping or associationstep, for example (and without limitation) as described in U.S. patentapplication Ser. No. 12/216,810, filed 10 Jul. 2008 and owned in commonwith the present application, which is hereby incorporated by referenceas if fully set forth herein.

Offline synchronization provides for synchronization that may beperformed in a stepwise manner comprising at least a two-phase processwhere at least one communication channels 117 or 118 is established. Afirst phase comprises established at least one of communication channels117 or 118 to allow for synchronization between mobile device 102 orserver 104 to synchronize with computer 115. Preferably in the secondphase of synchronization between computer 115 and mobile device 102 orserver 104 is performed depending on which device was not synchronizedin the first synchronization phase. Most preferably during the firstphase computer 115 acts as a server while synchronizing with mobiledevice 102 while in the second phase computer 115 acts as a client whilesynchronizing with server 104. Optionally a third phase may be providedfor accommodating an additional synchronization stage, which may berequired due to secondary or downstream changes that occur as a resultof the original synchronization process, in order to at least check forconsistency between computer 115 and mobile device 102 and/or server104, and optionally and preferably to also re-synchronize data wherenecessary.

Optionally during the first phase of offline synchronization computer115 may store synchronized data from the source device (mobile device102 or sever 104) locally, in local data stores, formats and orapplications associated with computer 115, for example a local calendarcomprising contact details, tasks such as Microsoft Outlook®, or storeother data types in local folders part of computer 115 file system forexample “My Pictures” or “My Documents” or “My Music” or the like.During a second phase of offline synchronization the synchronized datais converted to the appropriate data stores and format of the targetdevice (mobile device 102 or server 104, the opposite of that of phaseone).

FIG. 1A depicts the first optional embodiment of the present inventionshowing system 100 wherein agent 108 is associated with mobile device102. As described above most preferably agent 108 facilitatescommunication and data exchange within system 100.

Optionally and preferably agent 108 communicates with computer 115,through first communication channel 117 provided by an optional shortrange communication protocols for example including but not limited to aproprietary protocol, OBEX (object exchange) or the like short rangecommunication protocols over Bluetooth, Infrared, serial cable or thelike as is known in the art.

Preferably and optionally mobile device 102 comprises internal memory112. Optionally memory 112 may provide for internal mobile device 102functioning and/or applications, for example maintain phone bookapplications.

Agent 108 preferably facilitates data exchange for example data uploadand/or data download, between server 104 and mobile device 102 viacomputer 115. Optionally agent 108 facilitates data exchange through acellular/wireless network, for example through a gateway or other bridge(not shown) if computer 115 is not accessible.

Server 104 preferably comprises a database 114 for storing at least oneor more data, for example including but not limited to user data,calendar, user settings, phone setting or the like data associated withserver 104.

Database 114 may also optionally be used for storing one or more userconfiguration settings and/or one or more updates. Settings andconfiguration parameters are stored in database 114 and optionallydelivered to agent 108 upon installation and upgrade; optionally, if theuser made one or more changes (for example optionally through agent 108)then these change(s) are preferably stored in database 114 for deliveryto agent 108. This mechanism is central to achieve a smooth upgrade andto be able to control the settings of multiple devices for the sameaccount. In this manner the user does not have to define his/hersettings with each upgrade. The protocol also allows agent 108 to notifyserver 104 about changes that the user has made to his/her userpreferences through the UI of agent 108.

Server application 110 can optionally communicate with other servers inthe network (not shown) for transferring data sent from the cellulardevice 102 to the other servers (not shown), or for transferring datafrom the other servers (not shown) to the cellular device 102.

FIG. 1B is a schematic block diagram of system 101 according to anoptional second embodiment of the present invention wherein agent 108 isassociated with computer 115 functioning in the same manner as describedabove to facilitate data synchronization between server 104 and mobiledevice 102 in at least one of online or offline synchronization.Optionally and preferably within system 101 agent 108 periodically pullsinformation from the mobile device 102 optionally and preferably usingBluetooth profiles (forming communication channel 117) for exampleincluding but not limited to Generic Object Exchange Profile (GOEP),Synchronization Profile (SYNCH), File Transfer Profile (FTP), or thelike as is known in the art.

FIG. 2 is a schematic block diagram for an exemplary scenario fortransferring data from mobile device 102 to a content provider server104 via computer 115 as described in FIG. 1A where a user wishes totransfer content, for example an image from mobile device 102 to awebsite. In stage 201 the user manually activates agent 108, aspreviously described, optionally through a menu option in mobile device102. Optionally and preferably agent activation comprises a userproviding instructions and/or commands to agent 108 through the UserInterface of agent 108, which is optionally and preferably displayed onthe screen of device 102. For example, such user setting, instructionsand/or commands optionally include selection of the image, the finaldestination of the image as well as information relating to and/orassociated with the image to be transferred for example a caption orshort image description. Most preferably user settings, for exampleincluding but not limited to file destination, are preferably definedthrough a Web interface that may optionally and preferably, be providedby server 104. The user may preferably manage these settings, such asselecting destination sites and provide credentials or authorizationfrom computer 115 and/or device 102 preferably through a Web browser.Optionally, settings may be managed through the user interfaceassociated with agent 108. Next in stage 202 agent 108 associated withmobile device 102 (as in FIG. 1A) facilitates image transfer to computer115 preferably through a local communication channel 117 for exampleBluetooth. Next, in stage 203, computer 115 transfers the image tocontent server 104 preferably using long range communication channel 118for example the internet via HTTP protocol, over TCP/IP. Finally instage 204 image content server 104 transfers the image content to thefinal destination, as defined by the user in stage 201.

FIGS. 3A and 3B are schematic diagrams describing the push scenariosassociated with the data transfer and synchronization according to thepresent invention between a mobile device 102, acting as the datasender, and a computer 115 acting as the data receiver. According to anoptional embodiment of the present invention, data transferred frommobile device 102 to computer 115 as previously described may be eitherpushed or pulled. Most preferably during data push agent 108 that isoptionally and preferably associated with mobile device 102,periodically or upon request, transfers data from mobile device 102 tocomputer 115.

FIG. 3A describes a push synchronization scenario that may take placewith a first optional embodiment of the present invention as depicted inFIG. 1A relating to system 100 where data is transferred online(synchronously) between mobile device 102 and server 104 through bridgein the form of computer 115. Synchronized transfer is preferably usedwhen the computer 115 is connected to the server 104 and to the device102 at the time of the data transfer as described with respect to onlinesynchronization system above. In stage 301, agent 108 facilitates datasynchronization between mobile device 102 and computer 115. Aspreviously described agent 108 activation may be provided by at leastone or more methods for example including but not limited to manualactivation, server activation, or event based activation; for exampleagent 108 may be activated either periodically, or upon a request fromthe user. In stage 302, data is transmitted from the computer 115 to theserver 104, preferably through communication channel 118. Next in stage303, server 104 stores the data in an internal storage 114 for examplean internal database. Next in stage 304, server 104 transfers data backto computer 115. Finally, in stage 5 updated new data is transferred todevice 102 through computer 115.

FIG. 3B describes a scenario in which the data is transferred offline(asynchronously) in two phases. A-synchronized transferred is preferablyused when the computer 115 is temporary not connected to at least one ofserver 104, or mobile device 102 or when only one communication channel117 or 118 is available when attempting to transfer the data. First instage 311 data residing in mobile device 102 is communicated to computer115 over local communication channel 117. Optionally, stage 311 may beperformed either periodically, or upon a request from the user. Next instage 312, data originating from mobile device 102 is stored locally incomputer 115. Optionally, the data provided in a format specific tomobile device 102 may be converted to data specific to computer 115 forlocal storage. Optionally and preferably stages 311 and 312 form thefirst phase of offline or asynchronous data exchange while stages 313and 314 form the second phase of offline synchronization. Next in stage313 is preferably communication channels 118 is established optionallyand preferably between computer 115 and server 104 providing for datatransfer between computer 115 and server 104 for data transferred tocomputer 115 during stage 311 from mobile device 102 as described above.Next in stage 314, server 104 optionally and preferably transfers datatargeted for device 102 to computer 115, optionally data also remainsstored at the server. Next in stage 315 the device 102 targeted datafrom server 104 is optionally stored in computer 115. Optionally serverdata is provided in a format specific to server and/or mobile device 102may be converted to data specific to computer 115 for local storage.Next in stage 316 offline synchronization is completed when dataoriginating from server 104 data reaches its final destination mobiledevice 102 most preferably once short range and/or local communicationchannels 117 is established between computer 115 and device 102.

FIGS. 4A-B provide schematic diagrams describing the data pull scenarioboth with online synchronization, FIG. 4A, and offline synchronization,FIG. 4B, according to optional, illustrative, exemplary embodimentsaccording to the present invention. According to an optional embodimentof the present invention data pulling may be provided with mobile device102 optionally with or without an agent 108. Optionally if mobile device102 is not equipped with, and/or associated with and/or available toagent 108, data synchronization according to optional embodiments of thepresent invention may be provided for with a built-in Bluetooth agentprovided with mobile device 102 that optionally implements one or morestandard Bluetooth profiles. Optionally, such a Bluetooth profile allowsserver 104 to access data associated with mobile device 102 for exampleincluding but not limited to an address book, files, or the like.Optionally data pulling by computer 115 may provide for access tospecific data types otherwise not accessible by agent 108, for exampleincluding but not limited to message inbox and/or system files, or thelike.

FIG. 4A depicts an example of data pull synchronous or online datatransfer scenario between mobile device 102 and content computer 115.Online synchronized data transferred is preferably provided whencomputer 115 is actively connected to the server 104 and to mobiledevice essentially simultaneously through at least one and mostpreferably two communication channels 117 and 118 during data transfer.First in stage 401, application associated with computer 115 reads thedata from mobile device 102. Optionally and preferably stage 401 isperformed periodically. Next, in stage 402 computer 115 transfers datato server 104. Next in stage 403 data is stored in server 104.Independently to stages 401-403, server 104 may optionally transfer datato mobile device 102. In stage 404, server 104 optionally and preferablytransfers data to computer 115. Next in stage 405 data is optionally andpreferably transferred to mobile device 102. In addition data isoptionally stored in computer 115, preferably at least temporarily.

FIG. 4B describes a scenario in which the data is pulled in an offlineor asynchronously data transfer. Asynchronous transfer is optionally andpreferably used when computer 115 is temporary not connected to theserver 104, or to the device 102, at the time attempting to transfer thedata. First in stage 411, the application on the computer 115 reads thedata from device 102. Optionally stage 411 is preferably performedperiodically. Next in stage 412 the transferred data is stored incomputer 115. Next in stage 413 optionally performed when computer 102is re-connected to server 104, data is transferred to the server 104,optionally a copy of the transferred data is maintained in computer 115.Independently to stages 411-413, server 104 may optionally transfer datato device 102. In stage 414, server 104 optionally and preferablytransfers data to computer 115. Next in stage 415 the data is optionallystored in computer 115, at least temporarily until computer 115 isreconnected with the mobile device 102. Next in stage 416, optionallyand preferably performed when computer 115 is re-connected to mobiledevice 102, the data is preferably transferred directly to device 102.

FIG. 5 is a schematic diagram showing a further depiction of an optionalsystem according to the present invention as shown in FIGS. 1A-B.

State of the art applications show data transfer between a mobile device102, for example a mobile telephone, data synchronization server 104 viaa direct cellular and/or wireless network communication channel 140.However, communication channel 140 is expensive, non-reliable and mayprovide low bandwidth for data transfer applications between a mobiledevice 102 and server 104. Alternatively, fixed network communicationchannels for example in the form of a computer network do not sufferfrom such downfalls. According to an optional embodiment of the presentinvention, data is first transferred from mobile device 102 to acomputer 115 via a short range communication channels 117, such asBluetooth, for example and from computer 115 to data synchronizationserver 104 via long range communication channels and protocols 118, forexample provided with a fixed internet connection over DSL, Cables,Ethernet or other computer network 118. Communication channel 118 mayoptionally further provide for data exchange with auxiliary or thirdparty network servers 120 such as websites in the public for exampleFacebook, YouTube, or private domain for example bank accounts.

Agent 108 preferably facilitates data exchange for example data uploadand/or data download, between server 104 and mobile device 102 viacomputer 115. Optionally agent 108 may facilitate data exchange througha cellular/wireless network 140 if computer 115 is not accessible.Optionally network communication channel 140 may be further providedwith network-level gateways.

FIG. 6 provides a detailed description of an optional proxyauthentication process for authenticating both a user and mobile device102. Most preferably authentication is provided when agent 108communicates with server 104 indirectly via computer 115, according toan optional embodiment of the present invention wherein a computerapplication running on computer 115 serves as a proxy most preferablypassing all data to server 104. Preferably proxy authentication providesfor server 104 to detect new devices and/or hardware changes associatedwith mobile device 102, for example a SIM card replacement or changes,therein most preferably preventing fraud and/or errors. Without wishingto be limited in any way, proxy authentication is optionally initiatedin stage 601 with mobile device 102 authentication is provided forexample provided by authenticating device related data, MSISDN data (ifavailable), Bluetooth address data, IMSI, IMEI (GSM) or ESN (CDMA) orthe like data associated with the mobile device 102. Optionally server104 may allocate a unique Device ID during the detection of a new deviceinstance and use that for authentication. Optionally, a private key canbe used for applying a challenge-response mechanism for strongerauthentication.

Next in stage 602 user authentication of mobile device 102 is provided,for example by using username and password for user verification.Optionally, user authentication may be provided in at least one or moreof a plurality of methods as is known in the art for example MSISDNprovided by the network, user key that is provisioned upon activation.Following user and device authentication in stages 601 and 602, next instage 603, agent 108 provides server 104 with the authentication datamost preferably along with the encrypted data, for example encrypted byMD5 or the like protocol. Finally in stage 604 server 104 authenticatesthe data and user information optionally if the data is authenticatedthen a session identifier is provided by server 104.

FIG. 7 provides is a detailed description of an optional authenticationprocess undertaken between computer 115 and server 104 according to thepresent invention. Preferably computer 115 and server 104 authenticationis provided in a synchronization session which does not involve agent108. Optionally and preferably an application running on computer 115facilitates user authentication between computer 115 and server 104.

In stage 701 user configures user authentication details, for exampleusername and password, through an application running on computer 115.Next in stage 702 application 105 saves the authentication credentials.Next in stage 703 when mobile device 102 activates a new session withthe server 104, for example for transferring new data, then server 104authenticates the session via the user authentication data providedthrough a computer application running on computer 115.

FIG. 8 provides an optional method according to the present inventionfor double authentication process. This mode is preferably used when theconnection to the user can be done either through computer 115 orthrough the cellular network. In this mode, the computer applicationpreferably running on computer 115 is authenticated as a specific userin the server 104, with a username and password. The server 104 is alsoaware of the device 102 and it is assumed that the device is alreadyprovisioned in the system. When connecting to the server 104, thecomputer application preferably sends user credentials, and morepreferably also sends the identification of the device (Bluetoothaddress, private key, IMEI or other unique ID). The server 104preferably verifies that device 102 indeed belongs to the user (i.e. thedevice was provisioned for that specific user) and will allow tosynchronize with the user's account only if there is a match.

In stage 801, the user preferably initially provides a username andpassword through the application in the computer, most preferably whenactivating the application (one time). Next in stage 802, the device isregistered in the system and provisioned to a specific user, preferablythrough the application that is installed in the computer 115. Next instage 803 the registration information is kept on server 104. Next instage 804, when mobile device 102 activates a new data transfer sessionwith server 104 via a computer application running on computer 115, forexample, for transferring new data, server 104 authenticates the sessionusing at least two authentications, a first authentication from computer115 via a computer application, for example by requesting userauthentication data for example including username, password, questions,captcha, or the like; and a second authentication from mobile device 102information. Next in stage 805, when mobile device 102 activates a newsession with server 104 via the cellular network, for example fortransferring new data, then the server 104 optionally and preferablyalso authenticates the session via the agent by requesting information,including but not limited to MSISDN, user name/password, private key andso forth.

While the invention has been described with respect to a limited numberof embodiments, it will be appreciated that many variations,modifications and other applications of the invention may be made.

1. A method for data synchronization between a mobile device and acomputer network, using a computer as a bridge; comprising: Providing aplurality of mobile devices, each mobile device connected to a computerthrough a local network, each mobile device comprising digital contentfor transmitting to a server connecting to the internet network;Transmitting the digital content from said mobile device to saidcomputer directly without transmission through a mobile network;Transmitting said digital content from said computer to said server. 2.The method of claim 1 wherein said connection between said mobile deviceand said computer is wireless.
 3. The method of claim 2 wherein saidwireless connection is Bluetooth or Infrared.
 4. The method of claim 2wherein said wireless connection comprises Wi-Fi or Wi-MAX.
 5. Themethod of claim 1 wherein said connection between said mobile device andsaid computer is wired.
 6. The method of claim 5 wherein said wiredconnection is USB cable.
 7. The method of claim 1 wherein saidconnection between said computer and said server is over HTTP.
 8. Themethod of claim 1 wherein said digital content from said mobile deviceis pushed to said computer.
 9. The method of claim 1 wherein saiddigital content from said mobile device is pulled by said computer. 10.The method of claim 1 wherein said digital content, retrieved from saidmobile device, is transferred from the server to one or more serversconnected to the internet.
 11. The method of claim 1 wherein saiddigital content is saved and can be retrieved by said mobile device. 12.The method of claim 1 wherein said digital content is transferred fromone or more servers connected to the internet to said server and fromsaid server to said communication device.
 13. The method of claim 1,wherein the mobile device comprises a cellular telephone.
 14. A systemfor bridging and synchronization data between a mobile device and acomputer network, using a computer, comprising: A mobile device; Acomputer connected to said mobile device and to the internet; An agentinstalled on the computer; A server connected to the internet; and Dataobjects to be transferred from said mobile device to said server andfrom said server to said mobile device through the internet by saidagent and said computer.
 15. The system of claim 14 wherein saidconnection between said mobile device and said computer is wireless; 16.The system of claim 14 wherein said wireless connection is Bluetooth;17. The system of claim 14 wherein said wireless connection comprisesInfrared.
 18. The system of claim 14 wherein said connection betweensaid mobile device and said computer is wired.
 19. The method of claim18 wherein said connection between said computer and said server is overHTTP.
 20. The system of claim 14, further comprising an agent installedon said mobile device for initiating transferring commands by user andfor transferring said data to said computer.
 21. The system of claim 14wherein said agent installed on said computer bridges between saidcommunication device and said server for transferring data between saidpersonal device and said server.
 22. The system of claim 14 wherein saiddata is saved in a data base.
 23. The system of claim 22 wherein saidsaved data can be retrieved by the user of said computer.
 24. The systemof claim 14 wherein said server transfers said data to one or moreadditional servers via the internet.
 25. The system of claim 14 whereinsaid server receives digital content data from one or more servers viathe internet and transfers said data to said mobile devices via saidcomputer.
 26. The system of claim 14, wherein the mobile devicecomprises a cellular telephone.
 27. A method for proxy authentication;comprising; Authenticating the mobile device to a local computer toidentify a user; Authenticating said local computer to a remote serverto identify the user; and Authenticating the user to said remote serverthrough said local computer.